InBox DynamicFieldFromUser
Versão 6.0.4 Data de Criação 22/03/2019
Resources
The purpose of this module is to store attendant data in dynamic text fields in ticket creation (TicketCreate) or owner change (TicketOwnerUpdate) events.
Pré-requisitos
Framework
The following versions of the OTRS framework are supported:
- [6.0.x]
Modules
The following modules are required:
- InBox Core 6.20.7 or superior
Operational system
The following operating systems are required:
- [None]
Third Party Software
The following third-party software is required:
- [None]
Installation
bin/otrs.Console.pl Admin::Package::Install /path/to/InBox\ DynamicFieldFromUser-6.0.4.opm
Settings
Create a Dynamic Field
To use this module it is necessary to use a new or existing dynamic field. To add a new field, go to: "Administration > Overview > Dynamic Fields". Create a dynamic field with the “Text” option:
After creating the dynamic field, go to: "Administration > System Configuration". Search for “Ticket::Frontend::AgentTicketFreeText###DynamicField”. Add the created dynamic field and choose the option “1 – Enabled”:
Finally, go to "Administration > System Configuration" and search for "DynamicFieldFromUser::Mapping". When the screen loads, click on “Edit this definition”:
In the first item, on the left, write the name of the created dynamic field. In the second item, on the right, add the name of the variable you want to be mapped. The variable name can be:
- UserTitle: Title used for the attendant;
- UserLastname: Attendant's last name;
- UserLogin: Attendant login name;
- UserFullname: Attendant's full name;
- ValidID: Validity of the attendant;
- UserEmail: Attendant's email;
- UserID: Attendant ID;
- UserFirstname: First name of the attendant;
- UserSkin: Name of the skin used by the attendant;
- UserMobile: Attendant's mobile number;
- UserTimeZone: Time zone used by the attendant;
- Among other customizable information in the environment.
By saving the settings, the module will be working correctly.
Usage
The InBox DynamicFieldFromUser module is an event that maps information from the attendant to save in one (or more) dynamic text-type field(s), in the TicketCreate (call creation) or TicketOwnerUpdate (owner change) events and, therefore, there is no interface to show.